-
Notifications
You must be signed in to change notification settings - Fork 298
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: translation issue for change theme #8199
fix: translation issue for change theme #8199
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
A production App ID was automatically generated for this PR. (log)
Click here to copy & paste above information.
|
🚨 Lighthouse report for the changes in this PR:
Lighthouse ran with https://deriv-app-git-fork-mahdiyeh-deriv-93000-fixchangethemetr-45480a.binary.sx/ |
Codecov Report
@@ Coverage Diff @@
## master #8199 +/- ##
===========================================
+ Coverage 0.05% 20.73% +20.67%
===========================================
Files 117 1539 +1422
Lines 3425 35916 +32491
Branches 893 7012 +6119
===========================================
+ Hits 2 7448 +7446
- Misses 3423 27748 +24325
- Partials 0 720 +720
|
This PR is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This PR was closed because it has been stalled for 5 days with no activity. Please reopen it if needed. |
|
GitGuardian id | Secret | Commit | Filename | |
---|---|---|---|---|
- | Generic High Entropy Secret | 2ab1ebf | packages/account/src/Components/currency-selector/tests/currency-selector.spec.tsx | View secret |
- | Generic High Entropy Secret | 2ab1ebf | packages/account/src/Components/currency-selector/tests/currency-selector.spec.tsx | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secrets safely. Learn here the best practices.
- Revoke and rotate these secrets.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
Our GitHub checks need improvements? Share your feedbacks!
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
✨ PR has been merged by Paimon the Release Bot |
Changes:
Please include a summary of the change and which issue is fixed below:
When you need to add unit test
When you need to add integration test
Test coverage checklist (for reviewer)
Type of change